home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / p_man / cat3n / send.z / send
Encoding:
Text File  |  1998-10-20  |  8.1 KB  |  133 lines
  1.  
  2.  
  3.  
  4. sssseeeennnndddd((((3333NNNN))))                                                              sssseeeennnndddd((((3333NNNN))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _ssss_eeee_nnnn_dddd_,,,, _ssss_eeee_nnnn_dddd_tttt_oooo_,,,, _ssss_eeee_nnnn_dddd_mmmm_ssss_gggg - send a message from a socket
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_ssss_yyyy_ssss_////_tttt_yyyy_pppp_eeee_ssss_...._hhhh_>>>>
  13.  
  14.      _iiii_nnnn_tttt _ssss_eeee_nnnn_dddd_((((_iiii_nnnn_tttt _ssss_,,,, _cccc_hhhh_aaaa_rrrr _****_mmmm_ssss_gggg_,,,, _iiii_nnnn_tttt _llll_eeee_nnnn_,,,, _iiii_nnnn_tttt _ffff_llll_aaaa_gggg_ssss_))))_;;;;
  15.  
  16.      _iiii_nnnn_tttt _ssss_eeee_nnnn_dddd_tttt_oooo_((((_iiii_nnnn_tttt _ssss_,,,, _cccc_hhhh_aaaa_rrrr _****_mmmm_ssss_gggg_,,,, _iiii_nnnn_tttt _llll_eeee_nnnn_,,,, _iiii_nnnn_tttt _ffff_llll_aaaa_gggg_ssss_,,,, _cccc_aaaa_dddd_dddd_rrrr______tttt _tttt_oooo_,,,,
  17.          _iiii_nnnn_tttt _tttt_oooo_llll_eeee_nnnn_))))_;;;;
  18.  
  19.      _iiii_nnnn_tttt _ssss_eeee_nnnn_dddd_mmmm_ssss_gggg_((((_iiii_nnnn_tttt _ssss_,,,, _mmmm_ssss_gggg_hhhh_dddd_rrrr _****_mmmm_ssss_gggg_,,,, _iiii_nnnn_tttt _ffff_llll_aaaa_gggg_ssss_))))_;;;;
  20.  
  21. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  22.      _s is a socket created with _ssss_oooo_cccc_kkkk_eeee_tttt.  _ssss_eeee_nnnn_dddd, _ssss_eeee_nnnn_dddd_tttt_oooo, and _ssss_eeee_nnnn_dddd_mmmm_ssss_gggg are used to
  23.      transmit a message to another socket.  _ssss_eeee_nnnn_dddd may be used only when the
  24.      socket is in a _c_o_n_n_e_c_t_e_d state, while _ssss_eeee_nnnn_dddd_tttt_oooo and _ssss_eeee_nnnn_dddd_mmmm_ssss_gggg may be used at
  25.      any time.
  26.  
  27.      The address of the target is given by _t_o with _t_o_l_e_n specifying its size.
  28.      The length of the message is given by _l_e_n.  If the message is too long to
  29.      pass atomically through the underlying protocol, then the error _EEEE_MMMM_SSSS_GGGG_SSSS_IIII_ZZZZ_EEEE
  30.      is returned, and the message is not transmitted.
  31.  
  32.      No indication of failure to deliver is implicit in a _ssss_eeee_nnnn_dddd.  Return values
  33.      of -1 indicate some locally detected errors.
  34.  
  35.      If no buffer space is available at the socket to hold the message to be
  36.      transmitted, then _ssss_eeee_nnnn_dddd normally blocks, unless the socket has been placed
  37.      in non-blocking I/O mode [see _ffff_cccc_nnnn_tttt_llll(2)].  The _ssss_eeee_llll_eeee_cccc_tttt call may be used to
  38.      determine when it is possible to send more data.
  39.  
  40.      The _f_l_a_g_s parameter is formed by _OOOO_RRRRing one or more of the following:
  41.  
  42.      _MMMM_SSSS_GGGG______OOOO_OOOO_BBBB   Send out-of-band data on sockets that support this notion. The
  43.                underlying protocol must also support out-of-band data.
  44.                Currently, only _SSSS_OOOO_CCCC_KKKK______SSSS_TTTT_RRRR_EEEE_AAAA_MMMM sockets created in the _AAAA_FFFF______IIII_NNNN_EEEE_TTTT
  45.                address family support out-of-band data.
  46.  
  47.      _MMMM_SSSS_GGGG______DDDD_OOOO_NNNN_TTTT_RRRR_OOOO_UUUU_TTTT_EEEE
  48.                The _SSSS_OOOO______DDDD_OOOO_NNNN_TTTT_RRRR_OOOO_UUUU_TTTT_EEEE option is turned on for the duration of the
  49.                operation.  It is used only by diagnostic or routing programs.
  50.  
  51.      See _rrrr_eeee_cccc_vvvv(3N) for a description of the _mmmm_ssss_gggg_hhhh_dddd_rrrr structure.
  52.  
  53. RRRREEEETTTTUUUURRRRNNNN VVVVAAAALLLLUUUUEEEE
  54.      These calls return the number of bytes sent, or _----_1111 if an error occurred.
  55.  
  56. EEEERRRRRRRROOOORRRRSSSS
  57.      The calls fail if:
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. sssseeeennnndddd((((3333NNNN))))                                                              sssseeeennnndddd((((3333NNNN))))
  71.  
  72.  
  73.  
  74.      _EEEE_BBBB_AAAA_DDDD_FFFF               _s is an invalid descriptor.
  75.  
  76.      _EEEE_NNNN_OOOO_TTTT_SSSS_OOOO_CCCC_KKKK            _s is a descriptor for a file, not a socket.
  77.  
  78.      _EEEE_IIII_NNNN_VVVV_AAAA_LLLL              _t_o_l_e_n is not the size of a valid address for the
  79.                          specified address family.
  80.  
  81.      _EEEE_IIII_NNNN_TTTT_RRRR               The operation was interrupted by delivery of a signal
  82.                          before any data could be buffered to be sent.
  83.  
  84.      _EEEE_MMMM_SSSS_GGGG_SSSS_IIII_ZZZZ_EEEE            The socket requires that message be sent atomically,
  85.                          and the message was too long.
  86.  
  87.      _EEEE_WWWW_OOOO_UUUU_LLLL_DDDD_BBBB_LLLL_OOOO_CCCC_KKKK         The socket is marked non-blocking and the requested
  88.                          operation would block.
  89.  
  90.      _EEEE_NNNN_OOOO_MMMM_EEEE_MMMM              There was insufficient user memory available for the
  91.                          operation to complete.
  92.  
  93.      _EEEE_NNNN_OOOO_SSSS_RRRR               There were insufficient STREAMS resources available
  94.                          for the operation to complete.
  95.  
  96. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  97.      _ffff_cccc_nnnn_tttt_llll(2), _wwww_rrrr_iiii_tttt_eeee(2), _cccc_oooo_nnnn_nnnn_eeee_cccc_tttt(3N), _gggg_eeee_tttt_ssss_oooo_cccc_kkkk_oooo_pppp_tttt(3N), _rrrr_eeee_cccc_vvvv(3N), _ssss_oooo_cccc_kkkk_eeee_tttt(3N)
  98.  
  99. NNNNOOOOTTTTEEEESSSS
  100.      The type of address structure passed to _aaaa_cccc_cccc_eeee_pppp_tttt depends on the address
  101.      family.  UNIX domain sockets (address family _AAAA_FFFF______UUUU_NNNN_IIII_XXXX) require a
  102.      _ssss_oooo_cccc_kkkk_eeee_tttt_aaaa_dddd_dddd_rrrr______uuuu_nnnn structure as defined in _ssss_yyyy_ssss_////_uuuu_nnnn_...._hhhh; Internet domain sockets
  103.      (address family _AAAA_FFFF______IIII_NNNN_EEEE_TTTT) require a _ssss_oooo_cccc_kkkk_aaaa_dddd_dddd_rrrr______iiii_nnnn structure as defined in
  104.      _nnnn_eeee_tttt_iiii_nnnn_eeee_tttt_////_iiii_nnnn_...._hhhh.  Other address families may require other structures.  Use
  105.      the structure appropriate to the address family; cast the structure
  106.      address to a generic _cccc_aaaa_dddd_dddd_rrrr______tttt in the call to _ssss_eeee_nnnn_dddd and pass the size of the
  107.      structure in the _t_o_l_e_n argument.
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.